Systems and methods for blockchain validation of user identity and authority

ABSTRACT

Systems and methods are described for performing blockchain validation of user identity and authority. In various aspects one or more processors receive a first blockchain ID and a second blockchain ID, where each of the first blockchain ID and the second blockchain ID is associated with a user and is further associated with a first and second blockchain, respectively. A plurality of blockchain transactions may be aggregated where the plurality of blockchain transactions includes at least a first blockchain transaction associated with the first blockchain and a second blockchain transaction associated with the second blockchain. A first validation event providing a first indication of validity for the user may be identified based on the first blockchain transaction or the second blockchain transaction.

FIELD OF THE DISCLOSURE

The present disclosure generally relates blockchain-based networks, and,more particularly to determining user information from blockchaintransactions for authentication and validity purposes.

BACKGROUND

Conventional systems and methods use centralized databases or storagemechanisms to store user information and that can be used to identifyusers. This centralized database scheme typically allows updates andtransactions to occur only in a synchronous fashion, where transactionsstored in the database are serialized to occur one at a time. Suchtransactions are typically controlled and accessed by a single entity,for example, a company or private institution that controls thecentralized database or storage mechanism.

The single entity control paradigm can create issues where the userinformation can be useful for other purposes because the userinformation is typically precluded from use in other applications evenwhere the user is willing and able to give permission to use suchinformation. Moreover, the single entity that controls and accesses theuser may be reluctant to share the user information with other partiesfor a variety of privacy or business concerns.

BRIEF SUMMARY

The systems and methods described herein relate to user information asdetermined from blockchain-based transactions. In various embodiments, ablockchain may be a type of decentralized database network that keepsrecords of blockchain transactions, which are a type of digitaltransactions. Rather than having a single entity control a traditionaldatabase, a blockchain-based network can include a network of replicateddatabases that can be synchronized via a public network (e.g., theInternet), and, therefore visible to anyone within the network.Blockchain networks can also, however, be private with restrictedmembership similar to an intranet.

As described herein, when a blockchain transaction is executed, it canbe grouped together into a cryptographically protected block with otherblockchain transactions. In some embodiments, the block of blockchaintransactions may be for transactions that occurred within a specifictime period, such as within the last 10 minutes, and that are sent tothe entire network for updating and storage in the replicatedblockchain-based network. Members of the network, including computingnodes as described herein, can compete to validate the blockchaintransactions for the network. In various embodiments, the validatedtransactions may then be added to the blockchain with a timestamp inchronological order. In this way, new blocks of validated transactionscan be linked to older blocks, making a chain of blocks that make up theblockchain and show every transaction made in the history of thatblockchain. The blockchain can be updated at every node in theblockchain network such that the blockchain is replicated at every node,giving users of the blockchain network the ability to reconcile thetransactions of any node against any other node at any given time.

The blockchain-based network's decentralized, open, and cryptographicnature allows users to trust each other and execute blockchaintransactions in a peer-to-peer fashion, making the need for a singlecontrol entity obsolete. The blockchain-based network also providesenhanced security benefits, including discoursing and preventing hackingattacks that commonly impact single control entities such as banks. Forexample, if a hacker targeted a particular block in a blockchain, thehacker would not only need to hack into that specific block, but all ofthe proceeding blocks linked to that blockchain spanning the entirehistory of the blockchain. Moreover, the attacker would also need toperform the same hack on every blockchain in the network, which could bemillions, simultaneously, therefore making hacking a blockchaininfeasible.

Accordingly, as described herein, systems and methods are disclosed forvalidating a user of blockchain-based networks services, including theidentification and authority of such a user, based on one or more ofuser's blockchain accounts, profiles, or blockchain transactions. Thedisclosed systems and methods can aggregate various transactions fromone or more of a the user's blockchains and analyze those transactionsto identify any number of validation events (e.g., trigger events or redflags) for various use cases, for example, using a blockchain-basedtransactions or information therein to determine to withhold aninsurance claim check to a spouse of user where the user's blockchaintransactions indicate that the user was recently divorced.

In various embodiments, blockchain-based systems and methods aredisclosed for performing blockchain validation of user identity andauthority, where one or more processors can receive a first blockchainID and a second blockchain ID, and where each of the first blockchain IDand the second blockchain ID is associated with a user. In someembodiments, the first blockchain ID can be a first public keyassociated with a first private key, and the second blockchain ID can bea second public key associated with a second private key. As describedherein, public and private keys are cryptographic keys that typicallyare generated in a public-private key pairs and are used inblockchain-based networks to identify a user and protect a user'sresources on a blockchain-based network.

In some embodiments, the first blockchain ID can be associated with afirst blockchain and the second blockchain ID can be associated with asecond blockchain. In various embodiments, the first blockchain and/orthe second blockchain can also be associated certain blockchain typesincluding, for example, any of a bank-based blockchain, a bitcoin-basedblockchain, an insurance-based blockchain, a public blockchain, or aprivate blockchain. Each blockchain type may have differentcharacteristics or attributes that may cause the blockchain-basedvalidation system and methods to operate according to the blockchaintype. For example, where a blockchain is a private blockchain, and atleast in one embodiment, the blockchain-based validation system andmethods may receive an indication from the user as to whether a privatetransaction associated with the user may be accessed.

In some embodiments, a plurality of blockchain transactions may beaggregated where the plurality of blockchain transactions can include atleast a first blockchain transaction associated with the firstblockchain and a second blockchain transaction associated with thesecond blockchain. Based on the first blockchain transaction or thesecond blockchain transaction, a first validation event providing afirst indication of validity for the user may be identified. In someembodiments, the indication of validity can be used to authorize theuser for an activity as further describe herein.

In other embodiments, the blockchain-based validation system and methodsmay be further configured to identify a second validation event based onthe first blockchain transaction or the second blockchain transaction,where the second validation event provides a second indication ofvalidity for the user, such that the blockchain-based validation systemand methods may determine an updated indication of validity for the userbased upon the first validation event and the second validation event.

As described further herein, each of the first validation event and/orthe second validation event can be associated with various event typesincluding, for example, a property purchase event, a vehicle purchaseevent, a user-life event, a frequency-of-occurrence event, a significantfinancial event, a location event, or a disputed transaction event.

In some embodiments, the blockchain-based validation system and methodsmay be further configured to receive a security-based indicator for theuser (e.g., a biometrics security indicator such as a digital fingerprint), and provide an enhanced indication of validity for the userbased on the security-based indicator for the user and the firstvalidation event.

In various embodiments, systems and methods are disclosed for generatinga blockchain-based user profile. For example, a blockchain-based userprofile can be associated with a particular user (e.g., an insurancecustomer who is a user of the blockchain-based network) and can beupdated based on one or more of the user's blockchain transactions. Asdescribed herein, in one embodiment, the profile may be used as acustomer service tool where a customer service representative use theblockchain-based user profile to authenticate or validate the user,therefore, requiring less authentication/validation for users orcustomers with positive profiles, such as a blockchain-based userprofile that has little or no negative validation events. In otherembodiments, the user profiles may be used to provide benefits andincentives (e.g., insurance discounts or other benefits) to customerswith positive profiles. In other embodiments, premiums may be adjusted,for example, increased, for user's having profiles with negativeblockchain validation events.

In various embodiments, blockchain-based systems and methods aredisclosed for generating a blockchain-based user profile. In variousaspects, one or more blockchain IDs associated with a user may bereceived by one or more processors. Each blockchain ID can be associatedwith a corresponding blockchain in a blockchain-based network. One ormore blockchain transactions may be identified that are associated withthe one or more blockchain IDs such that a trust profile for the usercan be generated based on the one or more blockchain transactions. Insome embodiments, the trust profile can be generated also based onnon-blockchain transactions, as further described herein. The trustprofile can include user information determined from the one or moreblockchain transactions or from the non-blockchain transactions. In someembodiments, the user information can include, for example, user taxrecords, user bills, user social media information, or one or morephotos of the user.

In some embodiments, the blockchain-based systems and methods mayfurther be configured to receive a session blockchain ID from a remotecomputing device, where the session blockchain ID can be associated withthe user. The session blockchain ID may be used to facilitate a chatsession, wherein the chat session is operable to receive one or moremessages from the remote computing device and to transmit one or moremessages to the remote computing device. In some embodiment, the sessionblockchain ID can be a blockchain ID from one or more blockchain IDsassociated with the user. In another embodiment, the session ID and thetrust profile can be used to authorize the remote computing device toreceive the user information. In still a further embodiment, theblockchain-based system may be configured to request additional userinformation of the user from the remote computing device.

In other embodiments, the blockchain-based system may be furtherconfigured to receive an additional blockchain ID associated with theuser, where the additional blockchain ID is associated with anadditional blockchain, and where one or more additional blockchaintransactions are identified that are associated with the additionalblockchain ID. The trust profile may be updated for the user based onthe one or more additional blockchain transactions, such that the trustprofile is enhanced and includes additional user information determinedfrom the one or more additional blockchain transactions.

In some embodiments, the trust profile can be used to determine one ormore loyalty benefits for the user. In other embodiments, theblockchain-based system can update one or more accounts of the userbased on the trust profile as described herein.

Advantages will become more apparent to those of ordinary skill in theart from the following description of the preferred embodiments whichhave been shown and described by way of illustration. As will berealized, the present embodiments may be capable of other and differentembodiments, and their details are capable of modification in variousrespects. Accordingly, the drawings and description are to be regardedas illustrative in nature and not as restrictive.

BRIEF DESCRIPTION OF THE DRAWINGS

The Figures described below depict various aspects of the system andmethods disclosed therein. It should be understood that each Figuredepicts an embodiment of a particular aspect of the disclosed system andmethods, and that each of the Figures is intended to accord with apossible embodiment thereof. Further, wherever possible, the followingdescription refers to the reference numerals included in the followingFigures, in which features depicted in multiple Figures are designatedwith consistent reference numerals.

There are shown in the drawings arrangements which are presentlydiscussed, it being understood, however, that the present embodimentsare not limited to the precise arrangements and instrumentalities shown,wherein:

FIG. 1 illustrates an example network diagram depicting several nodes ina blockchain-based network.

FIG. 2 illustrates an embodiment of a blockchain that exemplifiesvarious blockchains as described herein.

FIG. 3A illustrates an embodiment of a blockchain-based user account orprofile in accordance with the disclosures herein.

FIG. 3B illustrates an embodiment depicting user blockchain transactionsassociated with the blockchain-based user account or profile of FIG. 3A.

FIG. 4 illustrates an example blockchain-based method for performingblockchain validation of user identity and authority.

FIG. 5 illustrates an example method for generating a blockchain-baseduser profile.

FIG. 6 illustrates an embodiment of a user trust profile associated withuser blockchain information.

The Figures depict preferred embodiments for purposes of illustrationonly. Alternative embodiments of the systems and methods illustratedherein may be employed without departing from the principles of theinvention described herein.

DETAILED DESCRIPTION

FIG. 1 illustrates an example network diagram depicting several nodes ina blockchain-based network 100. Node 1 102 is a computing node that canbe a computing device, such as a computing device of a user. Forexample, Node 1 102 can be a tablet device 104, a mobile phone 106, asmart phone 108, or a personal computer 110. In the embodiment of FIG.1, Node 1 102 is connected to computer network 140, where Node 1 102 iscapable of electronic communication with other nodes connected tocomputer network 140, including Node 2 112, Node 3 122, and Node 4 132.Computer network 140 can include wired or wireless types of electroniccommunication for the transmission of computer data, including, forexample, a local area network (LAN), a wide area network (WAN) (e.g.,the Internet), and may consist of one or more cellular networks.Computer network 140 may utilize several protocols or networkingstandards to facilitate transmission of computer data, including, forexample, Ethernet, TCP/IP protocols, the WiFi protocol, the Bluetoothprotocol, TDMA, CDMA, GSM, iDen, or similar protocols or technologies.

Node 2 112, for example, can represent a computing node that includesone or more server(s) 116 that may be accessed by any of the othernodes, including, for example, Node 1 112 over computer network 140.Server(s) 116 may also be accessed a local client device 114, forexample, by a representative or other user associated with Node 2 112 orserver(s) 116. Node 3 122 can include an additional computing device124, for example, a second user personal computer, connected to computernetwork 140. Node 4 132 can include a further computing device 134, suchas a server or other networked computing device, connected to computernetwork 140. While the embodiment of FIG. 1 depicts only Nodes 1-4(102-132), many more nodes, including many more computing devices, canbe connected to, and operable to communicate via, computer network 140in accordance with the embodiment disclosed herein. Each of the Nodes1-4 (102-132) can include one or more processors, one or more computermemories (including RAM or ROM based computer storage), one or morecommunication interfaces (including a wired or wireless interface) forfacilitating electronic communication over network 140, and/or one ormore output devices (such as a screen, and an input device, such as amouse, keyboard, touchscreen, or similar device).

In various embodiments herein, Nodes 1-4 (102-132) can communicate overcomputer network 140 in a client-server capacity, for example, usingrequests and responses via the Hyper Text Transfer Protocol (HTTP),Hyper Text Markup Language (HTML), and similar protocols and languages.In one embodiment, a computing device, such as server(s) 116 at Node 2112, can execute a webserver platform, including, for example, JavaServer Pages (JSP), Active Server Pages (ASP).NET, Ruby on Rails tofacilitate client-server communication. In the present embodiment, theserver(s) 116 at Node 2 112 could receive requests from other nodes, forexample, Node 1 102, Node 3 122, or Node 4 132. For example, in oneembodiment, personal computer 110 at Node 1 102 can send one or morerequests to server(s) 116 at Node 2 112 and receive related responses.The requests may be HTTP requests to retrieve one or more webpages,where server(s) 116 host a website and/or database for responding withHTML, or similar web language technologies (e.g., JavaScript, CSS,etc.), for rendering the one or more webpages on the personal computer110. In a similar embodiment, computing device 124 at Node 3 122 mayalso send requests to and receive responses from servers(s) 116. In anembodiment where Node 4 132 includes one or more server(s) 134,server(s) 116 may also communicate via computer network 140 withserver(s) 134, where server(s) 134 may include information or services,such as user information (e.g., user information not readily availableto server(s) 116, such as non-blockchain user information) or otherthird-party information or services (e.g., weather information, anartificial intelligence service, etc.), where server(s) 116 may accessthe information or services at server(s) 134 via computer network 140 ina client-server capacity.

In some embodiments, as described herein, Nodes 1-4 (102-132) mayfacilitate client-server based messaging, where a first computing deviceat a first node may engage in a messaging session, such as a chatsession, by sending and receiving one or more messages to and from asecond computing device. For example, in one embodiment, a first user onpersonal computer 110 at Node 1 102 may communicate via computer network140 with a second user on local client device 114 on server(s) 116 atNode 2 112 using computer messages as part of a chat session. The chatsession may include a chat window on one or more webpages provided byserver(s) 116 to local client device 114, where, text input into thechat window may cause the text to be sent to server(s) 116 and to localclient device 114 for display to the second user. In some embodiments,the chat window may be implemented as a chat-based JavaScript program onthe webpage as displayed by the personal computer 110, where thechat-based JavaScript program is capable of capturing the text in thechat window and transmitting the text via an HTTP request and a dataformat, for example, the Java Object Script Notation (JSON) format, toserver(s) 116. Other protocols or formats may, however, be usedsimilarly. The chat session may be used to facilitate validation of auser as described herein, where a user, on personal computer 110 at Node1 102, may seek validation from the second user at local client device114 on server(s) 116 at Node 2 112.

In various embodiments herein, Nodes 1-4 (102-132) form ablockchain-based network 100, which can include a type of decentralizednetwork. A blockchain-based network may be operable where each of theNodes 1-4 (102-132) includes a blockchain program. The blockchainprogram can perform functions such as validating and relaying blockchaintransactions as disclosed herein. In some embodiments, each of the Nodes1-4 (102-132) may join the blockchain-based network by installing theblockchain program, thereby instantiating a node as a blockchain enablednode. In various embodiments, the blockchain-based network may coexistwith the client-server based network, where each of Nodes 1-4 (102-132)may perform both blockchain functionality and client-serverfunctionality as described herein.

In the blockchain-based network 100, each Node 1-4 (102-132) can be anadministrator node that can administer, manage, update, and/or maintainone or more blockchains or blockchain transactions in one or moreblockchain networks. Accordingly, in at in some embodiments, theblockchain-based network can be decentralized, where no single node,e.g., any one of Node 1-4 (102-132) can control a particular blockchain,but instead, where every node can administer, manage, update, and/ormaintain the blockchains in the network 100.

In some embodiments, the blockchain-based network can be a bitcoinblockchain-based network, where each node may administer, manage,update, and/or maintain one or more bitcoin blockchains by “mining”bitcoins. Bitcoins can be mined where each of the nodes compete, bysolving computationally complex cryptographic algorithms, to update thebitcoin blockchain with new bitcoin transactions, where the winning nodereceives bitcoins as an incentive for updating the related blockchain.Every node participating in the blockchain-based network, regardless ofwhich node wins, updates the blockchain with the new transaction, asdescribed herein, such that each node has a copy of the updatedblockchain. In this way, each node takes responsibility foradministering, managing, updating, and/or maintaining the bitcoinblockchain.

Because each node in a blockchain-based network (e.g., Nodes 1-4(102-132) of blockchain-based network 100), can be responsible foradministering, managing, updating, and/or maintaining a blockchain, theblockchain-based network can serve as a distributed database, where nosingle node maintains the blockchain and every node can continuallyupdate and reconcile the blockchain, such that the blockchain ismaintained and updated across the network.

In various embodiments, blockchains may be public or private. In someembodiments, public blockchains include blockchains that can be accessedby any node on the network. For example, in an embodiment where Nodes1-4 (102-132) of blockchain-based network 100 are public, any node oruser could access the blockchain, and, therefore blockchain transactionsof blockchain-based network 100.

In other embodiments, private blockchains include blockchains that canbe accessed only by certain nodes, such as privileged nodes, or by usersof the blockchain-based network that provide security credentials (e.g.,passwords) to access the blockchain. In other embodiments, a privateblockchain may be made accessible where permission is provided to accessthe blockchain, such as, where a user provides permission to access ablockchain including the user's personal information, as furtherdescribed herein. For example, in an embodiment where Nodes 1-4(102-132) of blockchain-based network 100 are private, then onlyprivileged nodes or users could access the blockchain, and, thereforeblockchain transactions of blockchain-based network 100.

In various embodiments, storing information via a blockchain-basednetwork can provide enhanced security over a storing data in traditionalcentrally located database, including eliminating risks that come withdata being held centrally. For example, typical blockchain-basednetworks lack centralized points of vulnerability for computer hackersto attack. Specifically, no centralized version of this informationexists for a hacker to corrupt. Instead, each of the nodes (e.g., Nodes1-4 (102-132)) maintains a copy that can be analyzed and checked againstthe copies in each of the other nodes in order to reconcile a trueversion.

In addition, blockchain-based network security methods can useencryption technology. In various embodiments, users identify themselvesin a blockchain-based network with a blockchain ID. In some embodiments,the blockchain ID is an encryption-based public key. A public key can bea cryptographic key that is associated with a private key that togetherform a user's public-private key pair. The public-private key pair canbe used to execute transactions on a blockchain as described herein. Insome embodiments, for example, a user's public key can be a long,randomly-generated string of numbers, which serves as a user's addresson in a blockchain-based network. A user may engage in transactions onthe blockchain-based network, where the transactions gets recorded inthe blockchain as belonging to that address, e.g., as associated withthat user's public key.

In various embodiments, a user's private key can act as the user'spassword that gives its owner access to their transactions or otherdigital assets as stored on the blockchain on the blockchain network. Auser typically keeps the private key confidential to prevent otherblockchain users from altering or viewing the user's blockchain-basedinformation or making new transactions not authorized by the user.

In some embodiments, a public-private key pair can be generated for anyof Nodes 1-4 (102-132) using the aforementioned blockchain program, forexample, after the blockchain program is installed on a computing deviceat a particular node. In one embodiment, for example, Node 1 102 cangenerate its public-private key pair when the blockchain program isinstalled on personal computer 110.

In some embodiments, a public-private key can be used to authenticateblockchain transactions, for example, to verify that a transaction camefrom a particular blockchain user and that the blockchain transactionhas not been modified in the blockchain-based network 100. For example,in an embodiment where blockchain-based network 100 includesbitcoin-based blockchains, a first user at Node 1 102 can, via theblockchain program, generate a public-private key pair as describedherein. In the present embodiment, the first user can use his or herprivate key to, via the blockchain program, to digitally sign, and,therefore authenticate, a bitcoin transaction on the blockchain-basednetwork 100. In some embodiments, each user can transfer value toanother user by digitally signing a hash of the previous transaction andthe public key of the other user and adding these to the end of theblockchain. Users can verify the signatures of the blockchaintransactions in each block linked in a blockchain to verify the chain ofownership from one user to the next.

For example, in an embodiment regarding a bitcoin-based blockchain, abitcoin transaction may be for the payment of a credit card statementfor a credit card account associated with a user. As described furtherherein, a transaction can be created where the user makes a payment forhis or her credit card via bitcoins, where the user specifies atransaction value (e.g., the amount of bitcoins to make for the creditcard payment) and also the recipient of the bitcoins (e.g., the creditcard company). The user can sign the transaction with his or her privatekey. The private key will generate the user's digital signature for thetransaction. The user, using the blockchain program, can then submit theblockchain transaction to the blockchain-based network 100, where it maybe added to the relevant blockchain in the blockchain network, such asblockchain-based network 100. Any party (e.g., the credit card company)with the first user's public key can then verify (by using its ownblockchain program and the user's public key) that the transaction wasactually created by the user because only the user's public key cancorrectly decipher the user's digital signature, thereby providing proofof authenticity for the transaction.

As contemplated herein, the blockchain-based network 100 may alsoinclude other types of blockchains including, for example, a bank-basedblockchain, an insurance-based blockchain, a public blockchain, or aprivate blockchain as described herein.

In some embodiments, the blockchain based network 100 can check theconsistency of existing and new transactions, and information therein,by each of its nodes (e.g., Nodes 1-4 (102-132)) on a periodic basis. Insome embodiments, for example, each of the Nodes 1-4 (102-132) canreconcile every existing or new transaction in a blockchain, or inseveral blockchains, stored in each node in ten minute intervals, whereeach node communicates with other nodes to verify that the transactionsare consistent in each node of the network.

In various embodiments herein, new transactions are grouped into blockson a periodic basis to create or update blockchains in theblockchain-based network (e.g., network 100), where each block canconsist of one or more transactions that have been executed in that timeperiod. A next group of transactions can then be executed in the nexttime period and so on, each time period creating a new block to add to ablockchain in the blockchain network. Accordingly, multiple blocks ofrelated transactions can be linked together thereby creating ablockchain as described herein. Thus, data or information embeddedwithin a blockchain is embedded within the network as a whole. Inaddition, as described herein, in some embodiments, the blockchain canbe public or private based on the network within it is stored.

As described herein, the data within the network can be difficult for ahacker or other intruder to corrupt because the data is redundantlystored in various nodes (e.g., Nodes 1-4 (102-132)), which each providea check-and-balance on each other and also serve as a backup in theevent one or more of the other nodes fail.

FIG. 2 illustrates an embodiment of a blockchain 200 that exemplifiesvarious blockchains as described herein. Blockchain 200 depicts threeblocks, Block 1 202, Block 2 212, and Block 3 222, each containingblockchain transactions. While depicted with three blocks, where eachblockchain contains three transactions each, blockchain 200, or anygiven blockchain as contemplated herein, may consist of many more blockswith various numbers of transactions, including millions of blocks eachincluding different numbers of transactions.

In some embodiments, as described herein, each block can includetransactions from a particular time interval (e.g., all new blockchaintransactions are grouped into a block every 10 minutes). Each of thetransactions can be associated with a separate and unique transactionID, as shown in FIG. 2 and as further discussed for FIG. 3B. Forexample, Block 1 202 could consist of Transaction 1 206, Transaction 2207, and Transaction 3 208, where each of Transactions 1-3 (206-208) mayhave separate transaction IDs (transaction IDs 1-3) and could have beenanalyzed and stored by a blockchain-based network (e.g., analyzed andstored by Nodes 1-4 (102-132) and blockchain-based network 100 ofFIG. 1) in a first specific time interval (e.g., in a first 10 minuteinterval). Similarly, Block 2 212 could consist of Transaction 4 216,Transaction 5 217, and Transaction 6 218, where each of Transactions 4-6(216-218) may have separate transaction IDs (transaction IDs 4-6) andcould have been analyzed and stored by a blockchain-based network (e.g.,analyzed and stored by Nodes 1-4 (102-132) and blockchain-based network100 of FIG. 1) in a second time interval (e.g., in the next 10 minuteinterval). In addition, Block 2 could then be linked to Block 1 using ablock digest (e.g., Block Digest 204) as described further herein. Inaddition, Block 3 222 could consist of Transaction 7 226, Transaction 8227, and Transaction 9 228, where each of Transactions 7-9 (226-229) mayhave separate transaction IDs (transaction IDs 7-9) and could have beenanalyzed and stored by a blockchain-based network (e.g., analyzed andstored by Nodes 1-4 (102-132) and blockchain-based network 100 ofFIG. 1) in a third time interval (e.g., the next 10 minute interval). Inaddition, Block 3 could then be linked to Block 2 using a block digest(e.g., Block Digest 214) as described further herein. Accordingly, thelinked Blocks 1-3 (202, 212, 222) form blockchain 200.

The block digests 204, 214, and 224 of Block 1 202, Block 2 212, andBlock 3 222, respectively, link the each of the blocks together. In someembodiments, as depicted in FIG. 2, the block digests (204, 214, and224) may each include a hash value that serves as a digital proof ofwork for a block. In one embodiment, the hash value may be determined bythe blockchain-network nodes (e.g. Nodes 1-4 (102-1:32)), where the hashvalue is the solution to a computationally expensive math problem thatincludes as input all the text from several new unverified transactions,plus the digest of the most recent block, plus a random value. The inputvalues are may be used in a hash function, such as SHA-256, to generatethe hash value. As depicted in FIG. 2, each block may store the hashvalue of a previous block creating a link from one block to the next,and, therefore creating a blockchain. For example, Block 2 212 includesits own hash value 214 and also the hash value 204 of the previous Block1 202, such that a link is established in the blockchain 200. Similarly,Block 3 222, includes its own hash value 224 and also the hash value 214of the previous Block 2 212, such that a further link is established inthe blockchain 200. Block 1 is depicted with no previous hash, which, insome embodiments indicates that Block 1 is the genesis, or first, blockin the chain that each of the further blocks, including Block 2 212 andBlock 3 222 link back to either directly or indirectly as shown for FIG.2.

In some embodiments, the hash value may have a preferred format, such asa leading number of zeroes for the hash value. In such embodiments, theblockchain nodes, such as Nodes 1-4 (102-132) may compete to determinethe correctly formatted hash value, where the first node to compute thehash value may receive a reward, such as a bitcoin. Assuming the newblock is valid, it can become a part of the block chain.

FIG. 3A illustrates an embodiment of a blockchain-based user account orprofile 302 in accordance with the disclosures herein. In variousembodiments the blockchain-based user account or profile 302 may bestored or maintained in one or more computer memories, such as the oneor more computer memories of Nodes 1-4 (102-132) as described forFIG. 1. The data or other information associated with theblockchain-based user account or profile 302 may be stored in memory viaone or more databases, such as a relational database, including anOracle or MySQL database, or a NoSQL type database, such as MongoDBdatabase. In some embodiments, the blockchain-based user account 302 maybe maintained by every computing node (e.g., Nodes 1-4 (102-132)) thatthe user account is associated with, such as every blockchain the useraccount has a transaction for, where each computing node stores a copyof the user account in its one or more computer memories, such as thecomputer memories described for FIG. 1. In another embodiment, the useraccount may be maintained only by the node associated with the user,such as Node 1 102, where the account is part of the blockchain programexecuting on the users computing node, such as personal computer 110 asdescribed for FIG. 1. In a further embodiment, the users account may bemaintained by a third party, such as a third party provider who providesservices or products to the user, where the user account is maintainedremotely. For example, in such an embodiment an insurance provider couldmaintain the user's account 302 on server(s) 116 at Node 2 112, wherethe user could access the account 302 remotely from personal computer110 at Node 1 102.

In the embodiment of FIG. 3A, the blockchain-based user account 302includes user information 306 associated with a user, where the userinformation 306 includes personal information about the user, includingthe user's physical address or location, the user's email address, andphone number. Other information may be included about the user in theuser information 306 portion of the blockchain-based user account 302,where such other information could be information that furtheridentifies the user on (e.g., an account number, social security number,etc.). In some embodiment, other information may also includetransaction based information, such as non-blockchain transactioninformation such as tax filings or bank statements associated with theuser.

The blockchain-based user account 302 may also include account summaryinformation 304. The account summary information 304 may include theuser's account name, which can be the user's real name or an alternatename, such as an email address or screen name (e.g., “user 1” asdepicted for FIG. 3A). The account summary information 304 may alsoinclude blockchain-based information, such as the user's blockchainaddress on a given blockchain network, such as the blockchain-basednetwork 100 of FIG. 1. In some embodiments, the user's blockchainaddress can be the user's public key used to execute blockchaintransactions on the blockchain network as described herein. The user'sblockchain address can associate the user with transactions that thatthe user executed in a blockchain network. The account summaryinformation 304 may also include a hash value of the blockchain address,where, in the embodiment of FIG. 3A, for example, the hash value is ahash of the public key. In some embodiments, the hash value can be hash160 value, which can serve as a shortened address compared with theuser's blockchain address (e.g., public key), where, for example, a hash160 value of the user's public key can serve as a short address that canbe used to further identify the user on the block-chain based network,such as the blockchain-based network 100 of FIG. 1. While the embodimentof FIG. 3A depicts the user account having a single blockchain address,in other embodiments, the user's account may be associated with multipleblockchain addresses, each having, for example, separate public keys foruse in various blockchains or blockchain networks.

The account summary information 304 may also include informationregarding the number of block-chain transactions executed by the user.For example, in the embodiment of FIG. 3A, the user has executed 67transactions, which may be transactions associated with the blockchainfor the user's public key, e.g., “public key 1,” as shown in FIG. 3A. Inother embodiments, the blockchain transactions may indicate the totalnumber of blockchain transactions executed associated severalblockchains or blockchain networks.

FIG. 3B illustrates an embodiment depicting user blockchain transactions312 associated with the blockchain-based user account or profile 302 ofFIG. 3A. The blockchain transactions 312 may be associated with one ormore events, purchases, or other transactions that are were made via, ormaintained or stored by, a blockchain on a blockchain-based network(e.g., blockchain-based network 100). In one embodiment, each of theblockchain transactions 314-320 may be associated with a user'sblockchain address, such as the user blockchain address, e.g., “publickey 1”, of user account 302 of FIG. 3A.

Each of the blockchain transactions 314-320 can include a transactionID, a date stamp indicating a date or time at which the transaction wasmade, a blockchain address of the user who transmitted value (e.g., a“from” address), a blockchain address of a user who receives the value(e.g., a “to” address), an amount of the value that was transferred, anda description including information about the transaction. The value ofthe transaction can be in any type of currency, including, for example,in U.S Dollars (“$”) or in bitcoins (“BTC”).

For example, transaction 314 includes a transaction ID, “transaction ID1,” which, in some embodiments, can be an alphanumeric string thatuniquely identifies transaction 314 within a blockchain. The transaction314 can include a date time stamp (e.g., “2016-05-23 09:20:35”) whichindicates the date and time at which transaction 314 was executed.Blockchain transaction 314 also includes a blockchain address of theuser who transmitted value as indicated by the “From” address. Forblockchain transaction 314, the “From” address indicates public key 1 asassociated with user 1 of user account 302 of FIG. 3A. Accordingly, inthe embodiment of FIG. 3B, the blockchain transaction 314 is associatedwith user 1 of FIG. 3A as indicated by the public key 1, whereblockchain transaction 314 can be one of user 1's blockchaintransactions as executed for a blockchain in blockchain-based network100 of FIG. 1. Transaction 314 may have been executed on user 1'scomputing device, such as personal computer 110 of Node 1 102.Blockchain transaction 314 indicates that a second user, a user withblockchain address with “public key 2” received the value of thetransaction, here, for example, $639.57 U.S. Dollars, which is indicatedby the amount for blockchain transaction 314. Blockchain transaction 314also includes a description that indicates that blockchain transaction314 was for a “Credit Card Payment,” where, for example, in oneembodiment, blockchain transaction 314 could have been for a credit cardpayment by the user 1 at Node 1 102 to pay off a credit card statementassociated with a credit card account that user 1 holds with the seconduser (e.g., a credit card company) indicated at the public key 2 addressof blockchain transaction 314.

Similarly blockchain transaction 316 includes a transaction ID,“transaction ID 5,” which can be an alphanumeric string that uniquelyidentifies transaction 316 within a blockchain. The transaction 316includes a date time stamp (e.g., “2016-11-15 11:59:17”), whichindicates the date and time at which transaction 316 was executed.Blockchain transaction 316 also includes a blockchain address of theuser who transmitted value as indicated by the “From” address. Forblockchain transaction 316, the “From” address indicates public key 1 asassociated with user 1 of user account 302 of FIG. 3A. Accordingly, inthe embodiment of FIG. 3B, the blockchain transaction 316 is associatedwith user 1 of FIG. 3A as indicated by the public key 1, whereblockchain transaction 316 can be one of user 1's blockchaintransactions as executed for a blockchain in blockchain-based network100 of FIG. 1. Transaction 316 may have been executed on user 1'scomputing device, such as personal computer 110 of Node 1 102.Blockchain transaction 316 indicates that a second user, a user withblockchain address with “public key 103,” received the value of thetransaction, here, for example, $20,000.00 U.S. Dollars, which isindicated by the amount for blockchain transaction 316. Blockchaintransaction 314 also includes a description that indicates thatblockchain transaction 316 was for a “20 Percent Home Downpayment,”where, for example, in one embodiment, blockchain transaction 316 can beassociated with a life event of user 1, where user 1 puts 20 percentdown on the purchase of a home. The transaction could have been executedat Node 1 102, including, for example, at smart phone 108 associatedwith user 1, where the second user with public key 103 may be a bank,lender, mortgager, etc. associated with a loan the user receives for thebalance of the home purchase.

Similarly, blockchain transaction 318 includes a transaction ID,“transaction ID 7,” which can be an alphanumeric string that uniquelyidentifies transaction 318 within a blockchain. The transaction 318includes a date time stamp (e.g., “2017-04-23 14:20:16”), whichindicates the date and time at which transaction 318 was executed.Blockchain transaction 318 also includes a blockchain address of theuser who transmitted value as indicated by the “From” address. Forblockchain transaction 318, the “From” address indicates public key 1 asassociated with user 1 of user account 302 of FIG. 3A. Accordingly, inthe embodiment of FIG. 3B, the blockchain transaction 318 is associatedwith user 1 of FIG. 3A as indicated by the public key 1, whereblockchain transaction 318 can be one of user 1's blockchaintransactions as executed for a blockchain in blockchain-based network100 of FIG. 1. Transaction 318 may have been executed on user 1'scomputing device, such as personal computer 110 of Node 1 102.Blockchain transaction 318 indicates that a second user, a user withblockchain address with “public key 57” received the value of thetransaction, here, for example 0.01425791 bitcoins, which is indicatedby the amount for blockchain transaction 318. Blockchain transaction 318also includes a description that indicates that blockchain transaction318 was for a “Attorney Fee-Family Law Firm,” where, for example, in oneembodiment, blockchain transaction 318 can be associated with a lifeevent of user 1, such as a marriage event (e.g., marriage license), alife planning event (e.g., a user will), or a divorce event (e.g., whereuser 1 has engaged legal services regarding a divorce with a spouse).The transaction could have been executed at Node 1 102, including, forexample, at personal computer 110 associated with user 1, where thesecond user with public key 57 may be an attorney or law firm,associated with the Family Law Firm that received a payment for legalfees rendered.

Similarly, blockchain transaction 320 includes a transaction ID,“transaction ID 11,” which can be an alphanumeric string that uniquelyidentifies transaction 320 within a blockchain. The transaction 320includes a date time stamp (e.g., “2017-04-28 16:35:45”), whichindicates the date and time at which transaction 320 was executed.Blockchain transaction 320 also includes a blockchain address of theuser who transmitted value as indicated by the “From” address. Forblockchain transaction 320, the “From” address indicates public key 83,which may be a user of the blockchain-based network 100 of FIG. 1. Inthe embodiment of FIG. 3B, the blockchain transaction 320 is associatedwith user 1 of FIG. 3A as indicated by the public key 1, whereblockchain transaction 320 can be one of user 1's blockchaintransactions as executed for a blockchain in blockchain-based network100 of FIG. 1. Transaction 320 may have been executed by a computingdevice, such as such as server 134 of Node 4 132. Blockchain transaction320 indicates user 1 (having blockchain address with “public key 1”)received the value of the transaction, here, for example $1,563.89 U.S.Dollars, which is indicated by the amount for blockchain transaction320. Blockchain transaction 320 also includes a description thatindicates that blockchain transaction 320 was for a “Monthly DirectDeposit,” where, for example, in one embodiment, blockchain transaction320 can be associated with an event of user 1, such as a paycheck orpayment from user 1's employer (e.g., associated with server 134 at Node4 132) executing a blockchain transaction to pay the user 1 his or hermonthly salary via direct deposit into user 1's bank account.

It will be appreciated that while although only transactions 314-320 aredepicted and described for FIGS. 3A and 3B, a user, such as user 1, maybe associated with many more transactions, such as thousands oftransactions and across multiple blockchains, each from different spansof time, including spanning multiple years or decades, and eachassociated with different types of blockchains as described herein.

FIG. 4 illustrates an example blockchain-based method 400 for performingblockchain validation of user identity and authority. Method 400 may beexecuted on a node of a blockchain-based network, for example, any ofthe Nodes 1-4 (102-132) on blockchain-based network 100, where the nodecan execute instructions stored in the one or more computer memories ofthe node to execute method 400. Method 400 may begin (402) at block 404by receiving a first blockchain ID and a second blockchain ID, whereeach of the first blockchain ID and the second blockchain ID isassociated with a user. In some embodiments, for example, the user maybe a client or customer of an entity associated with theblockchain-based validation system as described herein. Theblockchain-based validation system may be located at one or more nodesin the blockchain-based network, including, for example, any of Nodes1-4 (102-132) on blockchain-based network 100.

In some embodiments, the first blockchain ID can be a first public keyassociated with a first private key and the second blockchain ID can bea second public key associated with a second private key, where each ofthe first public key and first private key, and the second public keyand the second private key, can be cryptographic public-private keypairs as described herein.

In some embodiments, the first blockchain ID can be associated with afirst blockchain and the second blockchain ID can be associated with asecond blockchain. Each of the blockchains may be blockchains maintainedby the blockchain-based network 100 of FIG. 1. In various embodiments,the first blockchain and/or the second blockchain can be associatedcertain blockchain types including, for example, any of a bank-basedblockchain, a bitcoin-based blockchain, an insurance-based blockchain, apublic blockchain, or a private blockchain.

In some embodiments, each blockchain type may have differentcharacteristics or attributes that can cause the blockchain-basedvalidation system and methods to operate according to the blockchaintype. For example, where a blockchain is a private blockchain, at leastin one embodiment, the blockchain-based validation system and methodsmay receive an indication from the user as to whether a privatetransaction associated with the private blockchain may be accessed. Inother embodiments, a user could specify what types of information isprivate. For example, the user may specify that information related tolife-events (e.g., marriage or child-birch events) is private. In suchembodiments, the validation system would not access such privateinformation. In some embodiments, the user's indication of validation,account, or profile, such as a trust profile, may be lowered to accountfor the decrease in information, such that a user that has indicatedprivate life-event information may receive more questions or challengeprompts when attempting to access a blockchain-based validation systemor otherwise interacting acting with the blockchain-based system orrelated representatives, such as a second user at local client device114 on Node 2 112 of FIG. 1.

At block 406 a plurality of blockchain transactions can be aggregatedwhere the plurality of blockchain transactions can include at least afirst blockchain transaction associated with the first blockchain and asecond blockchain transaction associated with the second blockchain.

At block 408, a first validation event providing a first indication ofvalidity for the user may be identified based on the first blockchaintransaction or the second blockchain transaction. For example, in oneembodiment, the indication of validity can be used to authorize the userfor an activity, for example, the activity of a user picking up aninsurance claim check for a supposed spouse. In various embodiments, theblockchain-based validation system may identify the first validationevent by scanning for factors in the blockchain transactions of a userto identify validation triggers, flags or events associated with theuser. In some embodiments, the transactions may indicate variousvalidation events based on the data within the transactions. Validationevents can include information determined from blockchain transactionsincluding, for example, life events such as a marriage event, a childbirth event, or divorce event. In other embodiments, a validation eventmay include information determined from a financial event, such ascredit card transaction event(s) or large financial events, such as thepurchase of a house, car, etc. In other embodiments, the frequency ofthe validation events may be considered, such as credit cardtransactions considered over a long or short period of time, where, forexample, payment of credit card statements over several years (with nolate payments, etc.) can indicate a high level of validity for the user.

In other embodiments the recency of a validation event may impact auser's indication of validity. For example, in such embodiments, atransaction that is dated later in time may provide a greater indicationof validity than an older transaction. For example, a transactionindicating a divorce event that occurred more recently than an oldertransaction indicating a marriage event may result in a decrease in anindication of validity for a particular user in a particularcircumstance, such as where a user requests to pick up an insuranceclaim check for a spouse, but where the user's blockchain transaction(s)indicate that the user has recently been divorced.

In some embodiments, the validation events may be assigned differentweights, where one validation event may impact a user's indication ofvalidity differently from a second validation event. In one embodiment,using the previous example, a divorce event may be assigned a higherweight than the marriage event where the divorce event occurred morerecently than the marriage event.

In some embodiments, a representative using the blockchain validationsystem, such as a representative at Node 2 112 on local client device114, can use the indication of validity to validate, or otherwiseauthorize, a user, e.g., for a given activity. For example, thevalidation may occur remotely, where a user or spouse of a userinteracts with a representative of the blockchain validation system viathe Internet or over the phone. In such embodiments, either the customeror spouse, or the user's or spouse's computing device, such as personalcomputer 110, may send one or more blockchain IDs to the representativesystem (such as server(s) 116 at Node 2 112) where the servers(s) 116can access the user's or spouse's blockchain information in theblockchain-based network 100 based on the provided blockchain IDs. Theblockchain transactions from the user's or spouse's blockchains can thenbe used to validate the user or spouse, or allow the representative toreview the history of the user or spouse. If the user's blockchaininformation is insufficient for validation, the representative may, atthat point, challenge the user or spouse such as, for example, askingadditional security questions, etc.

For example, the representative may validate a user requesting to pickup an insurance claim check, where the user's (and, in some embodiments,the spouse's) blockchain information contains a blockchain validationevent that provides an indication of validity below a certain validitythreshold. For example, in some embodiments as described herein, therepresentative could check a user trust profile with a trust factor thatindicates whether the user is authorized to pick up the check. With ahigh trust profile, the user may be authorized to pick up the check.However, for a low trust profile, the user may be denied or it may causethe representative to request additional information or contact thecustomer in order to obtain permission. In some embodiments, positivevalidation events could be that the user shares a common address andcredit card transactions with the spouse. In other embodiments, negativevalidation events could include a recent divorce event or an indicationthat the supposed spouse and the user now live at different addresses.Similarly, certain transactions can trigger negative validation eventsand, therefore, decrease an indication of validity for a user. Forexample, for a transaction that includes location information, such asthe address at which a purchase was made, and where the transactiondiffers substantially from a user's typical location, then suchtransaction may be considered fraudulent or could otherwise diminish theuser's indication of validity or at least the validity of the particularblockchain that the particular transaction is associated with.

In various embodiments, each blockchain transaction of a user can updatethe blockchain-based network 100, causing a user account or userprofile, such as a user trust account, to be updated accordingly. Forexample, in some embodiments, a user executing a new bitcoin-basedtransaction could be updated in the blockchain-based network 100 by eachof the Nodes 1-4 (102-132). In the present embodiment, a node, such asNode 2 112 may then analyze a user's profile for existing blockchain IDsand use the user's blockchain IDs to identify the new bitcoin-basedtransaction and update the user's account or profile as describedherein.

In some embodiments, the blockchain-based validation system and methodsmay be further configured to identify a second validation event based onthe first blockchain transaction or the second blockchain transaction,where the second validation event provides a second indication ofvalidity for the user, such that the blockchain-based validation systemand methods may determine an updated indication of validity for the userbased upon the first validation event and the second validation event.As described herein, some events can be more highly weighted than otherevents, where newer events can be more highly weighted than olderevents.

In addition, in some embodiments, the validation system may choose toignore one or more of the validation events, where the updatedvalidation event causes as past validation event to be ignored by thevalidation system. For example, where the first validation event is arecent divorce and the second validation event is a past marriage, thenthe second validation event can be ignored by the system.

In another embodiment, an updated validation event can be a combinationof the first validation event and second validation event, whichtogether create an enhanced validation event. For example, a firstvalidation event may be several years of credit card history showingthat the user is a responsible account holder (e.g., having a highcredit score) and a second validation event can be a bank direct depositaccount as determined from several bank-based blockchain transactionindicating that the user has a steady job and source of income. Togetherthese can create an enhanced validation event improving the user'sindication of validity.

In various embodiments, and as described herein, each of the firstvalidation event and/or the second validation event can be associatedwith various event types including, for example, a property purchaseevent, a vehicle purchase event, a user-life event (e.g., a marriedevent, a divorced event, a child-birth event, etc.), afrequency-of-occurrence event (e.g., multiple addresses, multiplepurchases events, etc.), a significant financial event (e.g., homepurchase event, car purchase event, tax filing event, etc.), a locationevent, or a disputed transaction event.

In some embodiments, a blockchain transaction may include a dispute froma user as to one or more blockchain transactions. For example, the usermay dispute that the transaction was entered into by the user or thatthe transaction was fraudulent or that an error occurred with respect tothe transaction. Such a transaction can serve as a validation event thatincreases the user's indication of validity by ignoring the disputedtransaction or by giving the transaction less weight in determining theindication of validity, e.g., from an aggregate of multipletransactions, where the disputed transaction is only one of multipleother non-disputed transactions.

In some embodiments, the blockchain-based validation system and methodsmay be further configured to receive a security-based indicator for theuser, and provide an enhanced indication of validity for the user basedon the security-based indicator for the user and the first validationevent. The security-based indicator could include, for example, abiometrics indicator such as an electronic finger print or an electronicvoice print, or the security-based indicator can be additionalinformation associated with the user such as a caller ID number of theuser or a password provided by the user.

FIG. 5 illustrates an example method 500 for generating ablockchain-based user profile. Method 500 may be executed on a node of ablockchain-based network, for example, any of the Nodes 1-4 (102-132) onblockchain-based network 100, where the node can execute instructionsstored in the one or more computer memories of the node to executemethod 500. For method 500, a trust relationship between a user and asecond entity can be established based on the user's history, asdetermined from the user's blockchain transactions and other information(e.g., non-blockchain information). The trust relationship may be usedto create a trust profile as described herein. The trust profile may beused, for example, to provide a user with enhanced client service, suchas allowing fewer security challenges for a trusted user. In otherembodiments, the trust profile may also be used to provide the user withfinancial benefits, including discounts or loyalty rewards for userswith sufficient trust profiles.

Method 500 begins (502) at block 504 where one or more blockchain IDsassociated with a user may be received, where each blockchain ID isassociated with a corresponding blockchain.

At block 506, one or more blockchain transactions may be identified thatare associated with the one or more blockchain IDs.

At block 508 a trust profile for the user can be generated based on theone or more blockchain transactions. In some embodiments, the trustprofile can be generated also be based on non-blockchain transactions,as further described herein, for example, with respect to FIG. 6. Thetrust profile can include user information determined from the one ormore blockchain transactions. In some embodiments, the user informationcan include, for example, user tax records, user bills, user socialmedia information, or one or more photos of the user.

In some embodiments, the blockchain-based systems and methods mayfurther be configured to receive a session blockchain ID from a remotecomputing device, where the session blockchain ID can be associated withthe user. The session blockchain ID may be used to facilitate a chatsession, wherein the chat session is operable to receive one or moremessages from the remote computing device and to transmit one or moremessages to the remote computing device. In some embodiments, thesession blockchain ID can be a blockchain ID from one or more blockchainIDs associated with the user. For example, a first user at Node 1 102can initiate a chat session with a second user at Node 2 11). The chatsession may be initiated, for example, via a web browser on personalcomputer 110 executing an HTML and JavaScript webpage provided byserver(s) 116 at Node 2 112. When the chat session is executed, forexample, by the first user selecting to initiate a chat session from thewebpage, the webpage may cause a request that includes the first user'sblockchain ID (e.g., the first user's public key) to be sent to theserver(s) 116 at Node 2 122. In one embodiment, the blockchain ID may bealready be associated with the first user's web browser such that theblockchain ID is sent automatically with the request. In anotherembodiment, the first user may have to specify the blockchain ID in theweb browser, such as on the web page, prior to executing the chatsession.

In the present embodiment, the server(s) 116 may use the blockchain IDto access the user's blockchain transactions associated with thatblockchain ID on the blockchain-based network, such as network 100. Insome embodiments, the server(s) 116 may also use the blockchain ID toidentify the user to access other information, e.g., non-blockchaininformation such as tax records, associated with the user in order toenrich the chat session. In other embodiments, the two or moreblockchain IDs may be sent from the user's web browser to sever(s) 116to further enhance the information about the user. In variousembodiments, an application at server(s) 116 may use the information,for example, to generate a trust profile based information taken fromone or more transactions from one or more blockchain IDs as describedherein, for example, for FIG. 6. In other embodiments, the second userat 114 may access the information to facilitate the chat session asdescribe herein.

In some embodiments, the blockchain ID may be a new blockchain ID of theuser not originally part of the one or more blockchain IDs used togenerate the trust profile. In another embodiment, the session ID andthe trust profile can be used to authorize the remote computing deviceto receive the user information. In still a further embodiment, theblockchain-based system may be configured to request additional userinformation of the user from the remote computing device in order toauthenticate the user in cases where not enough user information can bedetermined from the blockchain transactions alone. For example, thefirst user, via mobile computing device at Node 1 102, such as smartphone 108, can communicate with the second user, where the mobilecomputing device at Node 1 102 provides the blockchain ID.

In other embodiments the blockchain-based system may be furtherconfigured to receive an additional blockchain ID associated with theuser, where the additional blockchain ID is associated with anadditional blockchain, and where one or more additional blockchaintransactions are identified that are associated with the additionalblockchain ID. The trust profile may be updated for the user based onthe one or more additional blockchain transactions, such that the trustprofile is enhanced and includes additional user information determinedfrom the one or more additional blockchain transactions.

In some embodiments, the trust profile can be used to determine one ormore loyalty benefits for the user which can include, for example,insurance premium discounts, enhanced client service, etc. In otherembodiments, the blockchain-based system can update one or more accountsof the user based on the trust profile, for example, low trust profilescan indicate a higher risk user, such that a higher insurance premiummay be associated with a user having a low trust profile.

FIG. 6 illustrates an embodiment of a user trust profile 602 associatedwith user blockchain information. For example, in one aspect, the usertrust profile 602 may be associated with the user account or profile 302of FIG. 3A and the related user blockchain transactions 314-320 of FIG.3B. For example, in the embodiment of FIG. 6, user trust profile 602,includes the same user information 604 as the user information 306 offrom FIG. 3A. As described herein, the user trust profile 602 can bedetermined from the user's blockchain transactions. The trust profile602 may be determined from information within one or more transactionsacross one or more blockchains, including information from various pastblockchain transactions in different blockchain accounts for the userwhere the user has different blockchain IDs. As described herein,information can include, for example, whether the user has been married,for how long the user has been married, whether the user has beendivorced, when the user was divorced, the address or addressesassociated with the user, tax information (including tax returns) of theuser, or other user information. In various embodiments, the sources ofthe user information may be the user's bills, tax records, or otherinformation either taken directly from blockchain transactionsassociated with that information (e.g., a bitcoin transaction used topay a credit card bill) or non-blockchain transactions or information,as described below, such as the user's tax records that the user hasuploaded to the user's blockchain account or for purposes of creatingthe user profile.

For example, the user trust profile can be determined from blockchaintransactions 314-320 and related information as described for FIG. 3B.The user trust profile 602 may include the user's blockchain information606, which can include the user's email address or screen name (e.g.,“user 1” as depicted for FIG. 3A and for FIG. 6). The blockchaininformation 606 may also include one or more blockchain address(es)associated with the user, for example, public key 1, public key 8, andpublic key 23 as depicted for FIG. 6. It will be appreciated, however,than the user may have additional blockchain addresses. The blockchaininformation 606 may also include a total number of blockchaintransactions for the user, which can represent the total number ofblockchain transactions across all blockchains that the user isassociated with. Of that total number of blockchain transactions, theblockchain information 606 may also indicate which of those transactionsare “positive” or no-issue transactions, where such transactionsindicate a positive (or non-negative) validation event that can be usedto validate the user. The blockchain information 606 may also include atrust factor, which can be an enumerated value (e.g., “High,” “Medium,”or “Low” trust), based off the user's number of positive transactionscompared to the user's total transactions. In the embodiment of FIG. 6,for example, because the user has 271 positive transactions and 289total transactions, then a high correlation of positive transactionsexists and can result in the user receiving a “High” trust factor asshown.

In some embodiments, information received from other sources (e.g.,non-blockchain transactions 608) may also be associated with a user'sprofile. The information may include user information from social mediasources, such as a social media website such as Facebook or LinkedIn. Inother embodiments, non-blockchain transactions 608 may includeinformation regarding a user dispute, where the user could have providedinformation disputing a blockchain transaction, such as a blockchaintransaction that the user believes should not be associated with theuser's blockchain account or blockchain ID.

The user trust profile 602, and its related information, includingblockchain information 606, user information 604, and non-blockchaintransactions may be stored or maintained in memory or within a databaseassociated with any of the nodes of a blockchain-based network (e.g.,Nodes 1-4 (102-132) of blockchain-based network 100) as describedherein.

ADDITIONAL CONSIDERATIONS

Although the following text sets forth a detailed description ofnumerous different embodiments, it should be understood that the legalscope of the description is defined by the words of the claims set forthat the end of this patent and equivalents. The detailed description isto be construed as exemplary only and does not describe every possibleembodiment since describing every possible embodiment would beimpractical. Numerous alternative embodiments may be implemented, usingeither current technology or technology developed after the filing dateof this patent, which would still fall within the scope of the claims.

The following additional considerations apply to the foregoingdiscussion. Throughout this specification, plural instances mayimplement components, operations, or structures described as a singleinstance. Although individual operations of one or more methods areillustrated and described as separate operations, one or more of theindividual operations may be performed concurrently, and nothingrequires that the operations be performed in the order illustrated.Structures and functionality presented as separate components in exampleconfigurations may be implemented as a combined structure or component.Similarly, structures and functionality presented as a single componentmay be implemented as separate components. These and other variations,modifications, additions, and improvements fall within the scope of thesubject matter herein.

Additionally, certain embodiments are described herein as includinglogic or a number of routines, subroutines, applications, orinstructions. These may constitute either software (e.g., code embodiedon a machine-readable medium or in a transmission signal) or hardware.In hardware, the routines, etc., are tangible units capable ofperforming certain operations and may be configured or arranged in acertain manner. In example embodiments, one or more computer systems(e.g., a standalone, client or server computer system) or one or morehardware modules of a computer system (e.g., a processor or a group ofprocessors) may be configured by software (e.g., an application orapplication portion) as a hardware module that operates to performcertain operations as described herein.

The various operations of example methods described herein may beperformed, at least partially, by one or more processors that aretemporarily configured (e.g., by software) or permanently configured toperform the relevant operations. Whether temporarily or permanentlyconfigured, such processors may constitute processor-implemented modulesthat operate to perform one or more operations or functions. The modulesreferred to herein may, in some example embodiments, compriseprocessor-implemented modules.

Similarly, the methods or routines described herein may be at leastpartially processor-implemented. For example, at least some of theoperations of a method may be performed by one or more processors orprocessor-implemented hardware modules. The performance of certain ofthe operations may be distributed among the one or more processors, notonly residing within a single machine, but deployed across a number ofmachines. In some example embodiments, the processor or processors maybe located in a single location, while in other embodiments theprocessors may be distributed across a number of locations.

The performance of certain of the operations may be distributed amongthe one or more processors, not only residing within a single machine,but deployed across a number of machines. In some example embodiments,the one or more processors or processor-implemented modules may belocated in a single geographic location (e.g., within a homeenvironment, an office environment, or a server farm). In otherembodiments, the one or more processors or processor-implemented modulesmay be distributed across a number of geographic locations.

This detailed description is to be construed as exemplary only and doesnot describe every possible embodiment, as describing every possibleembodiment would be impractical, if not impossible. One may be implementnumerous alternate embodiments, using either current technology ortechnology developed after the filing date of this application.

Those of ordinary skill in the art will recognize that a wide variety ofmodifications, alterations, and combinations can be made with respect tothe above described embodiments without departing from the scope of theinvention, and that such modifications, alterations, and combinationsare to be viewed as being within the ambit of the inventive concept.

The patent claims at the end of this patent application are not intendedto be construed under 35 U.S.C. § 112(f) unless traditionalmeans-plus-function language is expressly recited, such as “means for”or “step for” language being explicitly recited in the claim(s). Thesystems and methods described herein are directed to an improvement tocomputer functionality, and improve the functioning of conventionalcomputers.

What is claimed is:
 1. A blockchain-based validation system configuredto perform blockchain validation of user identity and authority, theblockchain-based validation system comprising: a block-chain basedcomputing node communicatively coupled, via a blockchain network, to oneor more additional block-chain based computing nodes; a program memorycommunicatively coupled to the block-chain based computing node; andprogram instructions stored in the program memory that when executed bythe block-chain based computing node, cause the block-chain basedcomputing node to: receive, at the block-chain based computing node viathe blockchain network, a first blockchain ID and a second blockchainID, wherein each of the first blockchain ID and the second blockchain IDis associated with a user, the user being a same user of each of thefirst blockchain ID and the second blockchain ID, and wherein the firstblockchain ID is associated with a first blockchain and the where secondblockchain ID is associated with a second blockchain, aggregate, at theblock-chain based computing node, a plurality of blockchaintransactions, the plurality of blockchain transactions including atleast a first blockchain transaction associated with the firstblockchain and a second blockchain transaction associated with thesecond blockchain, identify, at the block-chain based computing node, anexisting first validation event based on the first blockchaintransaction or the second blockchain transaction, wherein each of thefirst blockchain transaction and the second blockchain transaction is anexisting transaction of the blockchain network that occurred prior tothe existing first validation event, and provide, via the block-chainbased computing node during an online session, a first indication ofvalidity for the user based on the existing first validation event. 2.The blockchain-based validation system of claim 1 further configured to:identify a second validation event based on the first blockchaintransaction or the second blockchain transaction, the second validationevent providing a second indication of validity for the user; anddetermine an updated indication of validity for the user based upon theexisting first validation event and the second validation event.
 3. Theblockchain-based validation system of claim 2, wherein each of theexisting first validation event and the second validation event isassociated with any of the following: a property purchase event, avehicle purchase event, a user-life event, a frequency-of-occurrenceevent, a significant financial event, a location event, or a disputedtransaction event.
 4. The blockchain-based validation system of claim 1further configured to authorize the user for an activity based on theindication of validity.
 5. The blockchain-based validation system ofclaim 1 further configured to: receive a security-based indicator forthe user; and provide an enhanced indication of validity for the userbased on the security-based indicator for the user and the existingfirst validation event.
 6. The blockchain-based validation system ofclaim 1, wherein the first blockchain ID is a first public keyassociated with a first private key, and wherein the second blockchainID is a second public key associated with a second private key.
 7. Theblockchain-based validation system of claim 1, wherein either of thefirst blockchain or the second blockchain are associated with any of oneor more of the following: a bank-based blockchain, a bitcoin-basedblockchain, an insurance-based blockchain, a public blockchain, or aprivate blockchain.
 8. The blockchain-based validation system of claim7, wherein at least one of the first blockchain or the second locationis a private blockchain, the blockchain-based validation system furtherconfigured to: receive an indication from the user as to whether aprivate transaction associated with the private blockchain may beaccessed.
 9. A blockchain-based validation method of performingblockchain validation of user identity and authority at one or moreblock-chain based computing nodes, the blockchain-based validationmethod comprising: receiving a first blockchain ID and a secondblockchain ID, wherein each of the first blockchain ID and the secondblockchain ID is associated with a user, the user being a same user ofeach of the first blockchain ID and the second blockchain ID, andwherein the first blockchain ID is associated with a first blockchainand the second blockchain ID is associated with a second blockchain;aggregating a plurality of blockchain transactions, the plurality ofblockchain transactions including at least a first blockchaintransaction associated with the first blockchain and a second blockchaintransaction associated with the second blockchain; identifying anexisting first validation event based on the first blockchaintransaction or the second blockchain transaction, wherein each of thefirst blockchain transaction and the second blockchain transaction is anexisting transaction of the blockchain network that occurred prior tothe existing first validation event; and; providing, during an onlinesession, a first indication of validity for the user based on theexisting first validation event.
 10. The blockchain-based validationmethod of claim 9 further configured to: identify a second validationevent based on the first blockchain transaction or the second blockchaintransaction, the second validation event providing a second indicationof validity for the user; and determine an updated indication ofvalidity for the user based upon the existing first validation event andthe second validation event.
 11. The blockchain-based validation methodof claim 10, wherein each of the existing first validation event and thesecond validation event is associated with any of the following: aproperty purchase event, a vehicle purchase event, a user-life event, afrequency-of-occurrence event, a significant financial event, a locationevent, or a disputed transaction event.
 12. The blockchain-basedvalidation method of claim 9 further configured to authorize the userfor an activity based on the indication of validity.
 13. Theblockchain-based validation method of claim 9 further configured to:receive a security-based indicator for the user; and provide an enhancedindication of validity for the user based on the security-basedindicator for the user and the existing first validation event.
 14. Theblockchain-based validation method of claim 9, wherein the firstblockchain ID is a first public key associated with a first private key,and wherein the second blockchain ID is a second public key associatedwith a second private key.
 15. The blockchain-based validation method ofclaim 9, wherein either of the first blockchain or the second blockchainare associated with any of one or more of the following: a bank-basedblockchain, a bitcoin-based blockchain, an insurance-based blockchain, apublic blockchain, or a private blockchain.
 16. The blockchain-basedvalidation method of claim 15, wherein at least one of the firstblockchain or the second location is a private blockchain, theblockchain-based validation system further configured to: receive anindication from the user as to whether a private transaction associatedwith the private blockchain may be accessed.
 17. A tangible,non-transitory computer-readable medium storing instructions forperforming blockchain validation of user identity and authority, whenexecuted by one or more processors of a first computing device, causethe first computing device to: receive a first blockchain ID and asecond blockchain ID from a second computing device, wherein each of thefirst blockchain ID and the second blockchain ID is associated with auser, the user being a same user of each of the first blockchain ID andthe second blockchain ID, and wherein the first blockchain ID isassociated with a first blockchain and the second blockchain ID isassociated with a second blockchain; aggregate a plurality of blockchaintransactions, the plurality of blockchain transactions including atleast a first blockchain transaction associated with the firstblockchain and a second blockchain transaction associated with thesecond blockchain; and identify an existing first validation event basedon the first blockchain transaction or the second blockchaintransaction, wherein each of the first blockchain transaction and thesecond blockchain transaction is an existing transaction of theblockchain network that occurred prior to the existing first validationevent; and provide, during an online session, a first indication ofvalidity for the user based on the first validation event.
 18. Thetangible, non-transitory computer-readable medium of claim 17, whereinthe non-transitory computer-readable medium further includesinstructions that, when executed by the one or more processors, causethe first computing device to: identify a second validation event basedon the first blockchain transaction or the second blockchaintransaction, the second validation event providing a second indicationof validity for the user; and determine an updated indication ofvalidity for the user based upon the existing first validation event andthe second validation event.
 19. The tangible, non-transitorycomputer-readable medium of claim 17, wherein the non-transitorycomputer-readable medium further includes instructions that, whenexecuted by the one or more processors, cause the first computing deviceto: generate a new blockchain transaction of the user based on the firstindication of validity for the user; and update the first blockchainwith the new blockchain transaction.
 20. The tangible, non-transitorycomputer-readable medium of claim 19, wherein the non-transitorycomputer-readable medium further includes instructions that, whenexecuted by the one or more processors, cause the first computing deviceto: update the second blockchain with the new blockchain transaction.